Debug operations on artificial intelligence operations

ABSTRACT

The present disclosure includes apparatuses and methods related to performing a debug operation on an artificial intelligence operation. An example apparatus can include a number of memory arrays and a controller, wherein the controller is configured to perform an artificial intelligence (AI) operation on data stored in the number of memory arrays and perform a debug operation on the AI operation.

TECHNICAL FIELD

The present disclosure relates generally to memory devices, and more particularly, to apparatuses and methods for debug operations on artificial intelligence operations.

BACKGROUND

Memory devices are typically provided as internal, semiconductor, integrated circuits in computers or other electronic devices. There are many different types of memory including volatile and non-volatile memory. Volatile memory can require power to maintain its data and includes random-access memory (RAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (SDRAM), among others. Non-volatile memory can provide persistent data by retaining stored data when not powered and can include NAND flash memory, NOR flash memory, read only memory (ROM), Electrically Erasable Programmable ROM (EEPROM), Erasable Programmable ROM (EPROM), and resistance variable memory such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), among others.

Memory is also utilized as volatile and non-volatile data storage for a wide range of electronic applications. Non-volatile memory may be used in, for example, personal computers, portable memory sticks, digital cameras, cellular telephones, portable music players such as MP3 players, movie players, and other electronic devices. Memory cells can be arranged into arrays, with the arrays being used in memory devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an apparatus in the form of a computing system including a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIG. 2 is a block diagram of a number of registers on a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIGS. 3A and 3B are block diagrams of a number of bits in a number of registers on a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIG. 4 is a block diagram of a number of blocks of a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure

FIG. 5 is a flow diagram illustrating an example artificial intelligence process in a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIG. 6A is a block diagram of an apparatus in the form of a computing system including a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIG. 6B is block diagram of an apparatus in the form of a computing system including a memory device having a shared input/out (I/O) line in a data path local to bank sections of an array with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure.

FIG. 7 is a schematic diagram illustrating sensing circuitry of a memory device, the sensing circuitry including a compute component, in accordance with a number of embodiments of the present disclosure.

FIG. 8 is a schematic diagram illustrating circuitry for a plurality of shared I/O lines in a data path of an array in accordance with a number of embodiments of the present disclosure.

FIG. 9A is a block diagram example illustrating a plurality of sections of an array coupled to a compute unit, having a plurality of logic stripes, by a plurality of shared I/O lines in a data path local to the array.

FIG. 9B is a block diagram example illustrating a plurality of arrays coupled to a plurality of compute components in a compute unit by a plurality of shared I/O lines in a data path local to the arrays where the compute component has a pitch equal to that of the data path of a shared I/O line and which is a multiple of a pitch of the digit lines to the array.

DETAILED DESCRIPTION

The present disclosure includes apparatuses and methods related to performing debug operations on artificial intelligence operations. An example apparatus can include a number of memory arrays and a controller configured to perform an artificial intelligence (AI) operation on data stored in the number of memory arrays and perform a debug operation on the AI operation. The debug operation can include stopping the AI operation and storing errors of the AI operation and results of the debug operation in temporary memory blocks of the number of memory arrays.

In some examples, a register of the controller can be used to perform the debug operations. To start the debug operation, a first bit of the register can be programmed to a first state and to stop and/or prevent the debug operation, the first bit of the register can be programmed to a second state. The controller can program the bits and/or bits of the register to particular states in response to receiving a command from the host, for example. A different register of the controller can define the layer where the debug operations will stop the A operation, change the content of the neural network, change the bias values, change the activation functions, observe the output of the layer, send the output of the layer, and/or send data.

Performing a debug operation on an artificial intelligence operation by stopping the AI operation and storing errors of the AI operation and results of the debug operation can improve reliability of the memory device. For example, the memory device can detect and correct errors and update input data, bias values, activation functions, and/or the neural network based on the detected and corrected errors to prevent future errors.

In the following detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how a number of embodiments of the disclosure may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the embodiments of this disclosure, and it is to be understood that other embodiments may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the present disclosure. As used herein, the designator “N” indicates that a number of the particular feature so designated can be included with a number of embodiments of the present disclosure.

As used herein, “a number of” something can refer to one or more of such things. For example, a number of memory devices can refer to one or more of memory devices. Additionally, designators such as “N”, as used herein, particularly with respect to reference numerals in the drawings, indicates that a number of the particular feature so designated can be included with a number of embodiments of the present disclosure.

The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate various embodiments of the present disclosure and are not to be used in a limiting sense.

FIG. 1 is a block diagram of an apparatus in the form of a computing system 100 including a memory device 120 in accordance with a number of embodiments of the present disclosure. As used herein, a memory device 120, memory arrays 125-1, . . . 125-N, memory controller 122, and/or AI accelerator 124 might also be separately considered an “apparatus.”

As illustrated in FIG. 1, host 102 can be coupled to the memory device 120. Host 102 can be a laptop computer, personal computers, digital camera, digital recording and playback device, mobile telephone, PDA, memory card reader, interface hub, among other host systems, and can include a memory access device, e.g., a processor. One of ordinary skill in the art will appreciate that “a processor” can intend one or more processors, such as a parallel processing system, a number of coprocessors, etc.

Host 102 includes a host controller 108 to communicate with memory device 120. The host controller 108 can send commands to the memory device 120. The host controller 108 can communicate with the memory device 120, memory controller 122 on memory device 120, and/or the AI accelerator 124 on memory device 120 to perform AI operations, read data, write data, and/or erase data, among other operations. AI accelerator 124 can also include components described in associated with FIGS. 6A-9B that are configured to perform AI operations. AI operations may include machine learning or neural network operations, which may include training operations or inference operations, or both. In some example, each memory device 120 may represent a layer within a neural network or deep neural network (e.g., a network having three or more hidden layers). Or each memory device 120 may be or include nodes of a neural network, and a layer of the neural network may be composed of multiple memory devices or portions of several memory devices 120. Memory devices 120 may store weights (or models) for AI operations in memory arrays 125.

A physical host interface can provide an interface for passing control, address, data, and other signals between memory device 120 and host 102 having compatible receptors for the physical host interface. The signals can be communicated between host 102 and memory device 120 on a number of buses, such as a data bus and/or an address bus, for example.

Memory device 120 can include controller 120, AI accelerator 124, and memory arrays 125-1, . . . , 125-N. Memory device 120 can be a low-power double data rate dynamic random access memory, such as a LPDDR5 device, and/or a graphics double data rate dynamic random access memory, such as a GDDR6, GDDR7, LPDDR6, DDR4, among other types of devices. Memory arrays 125-1, . . . , 125-N can include a number of memory cells, such as volatile memory cells (e.g., DRAM memory cells, among other types of volatile memory cells) and/or non-volatile memory cells (e.g., RRAM memory cells, among other types of non-volatile memory cells). Memory device 120 can read and/or write data to memory arrays 125-1, . . . , 125-N. Memory arrays 125-1, . . . , 125-N can store data that is used during AI operations performed on memory device 120. Memory arrays 125-1, . . . , 125-N can store inputs, outputs, weight matrix and bias information of a neural network, and/or activation functions information used by the AI accelerator to perform AI operations on memory device 120.

The host controller 108, memory controller 122, and/or AI accelerator 124 on memory device 120 can include control circuitry, e.g., hardware, firmware, and/or software. In one or more embodiments, the host controller 108, controller memory 122, and/or AI accelerator 124 can be an application specific integrated circuit (ASIC) coupled to a printed circuit board including a physical interface. Registers 130 can be located on memory controller 122, A accelerator 124, and/or in memory arrays 125-1, . . . , 125-N and be accessible by controller 122. Also, memory controller 122 on memory device 120 can include registers 130. Registers 130 can be programmed to provide information for the AI accelerator to perform AI operations. Registers 130 can include any number of registers. Registers 130 can be written to and/or read by host 102, memory controller 122, and/or AI accelerator 124. Registers 130 can provide input, output bias, neural network, and/or activation functions information for AI accelerator 124. Registers 130 can include mode register 131 to select a mode of operation for memory device 120. The AI mode of operation can be selected by writing a word to register 131, such as 0xAA and/or 0x2AA, for example, which inhibits access to the registers associated with normal operation of memory device 120 and allows access to the registers associated with AI operations. Also, the AI mode of operation can be selected using a signature that uses a crypto algorithm that is authenticated by a key stored in the memory device 120.

AI accelerator 124 can include hardware 126 and/or software/firmware 128 to perform AI operations. Also, AI accelerator 124 can also include components described in associated with FIGS. 6A-9B that are configured to perform AI operations. Hardware 126 can include adder/multiplier 126 to perform logic operations associated with AI operations. Memory controller 122 and/or AI accelerator 124 can received commands from host 102 to perform AI operations. Memory device 120 can perform the AI operations requested in the commands from host 102 using the AI accelerator 124, data in memory arrays 125-1, . . . , 125-N, and information in registers 130. The memory device can report back information, such as results and/or error information, for example, of the AI operations to host 120. The A operations performed by AI accelerator 124 can be performed without use of an external processing resource.

The memory arrays 125-1, . . . , 125-N can provide main memory for the memory system or could be used as additional memory or storage throughout the memory system. Each memory array 125-1, . . . , 125-N can include a number of blocks of memory cells. The blocks of memory cells can be used to store data that is used during AI operations performed by memory device 120. Memory arrays 125-1, . . . , 125-N can include DRAM memory cells, for example. Embodiments are not limited to a particular type of memory device. For instance, the memory device can include RAM, ROM, DRAM, SDRAM, PCRAM, RRAM, 3D XPoint, and flash memory, among others.

By way of example, memory device 120 may perform an AI operation that is or includes one or more inference steps. Memory arrays 125 may be layers of a neural network or may each be individual nodes and memory device 120 may be layer; or memory device 120 may be a node within a larger network. Additionally or alternatively, memory arrays 125 may store data or weights, or both, to be used (e.g., summed) within a node. Each node (e.g., memory array 125) may combine an input from data read from cells of the same or a different memory array 125 with weights read from cells of memory array 125. Combinations of weights and data may, for instance, be summed within the periphery of a memory array 125 or within hardware 126 using adder/multiplier 127. In such cases, the summed result may be passed to an activation function represented or instantiated in the periphery of a memory array 125 or within hardware 126. The result may be passed to another memory device 120 or may be used within AI accelerator 124 (e.g., by software/firmware 128) to make a decision or to train a network that includes memory device 120.

A network that employs memory device 120 may be capable of or used for supervised or unsupervised learning. This may be combined with other learning or training regimes. In some cases, a trained network or model is imported or used with memory device 120, and memory device's 120 operations are primarily or exclusively related to inference.

The embodiment of FIG. 1 can include additional circuitry that is not illustrated so as not to obscure embodiments of the present disclosure. For example, memory device 120 can include address circuitry to latch address signals provided over I/O connections through I/O circuitry. Address signals can be received and decoded by a row decoder and a column decoder to access the memory arrays 125-1, . . . , 125-N. It will be appreciated by those skilled in the art that the number of address input connections can depend on the density and architecture of the memory arrays 125-1, . . . , 125-N.

FIG. 2 is a block diagram of a number of registers on a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure. Registers 230 can be AI registers and include input information, output information, neural network information, and/or activation functions information, among other types of information, for use by an AI accelerator, a controller, and/or memory arrays of a memory device (e.g., AI accelerator 124, memory controller 122, and/or memory arrays 125-1, . . . , 125-N in FIG. 1). Registers can be read and/or written to based on commands from a host, an AI accelerator, and/or a controller (e.g., host 102, A accelerator 124, memory controller 122 in FIG. 1).

Register 232-0 can define parameters associated with AI mode of the memory device. Bits in register 232-0 can start A operations, restart A operations, indicate content in registers is valid, clear content from registers, and/or exit from AI mode.

Registers 232-1, 232-2, 232-3, 232-4, and 232-5 can define the size of inputs used in AI operations, the number of inputs used in A operations, and the start address and end address of the inputs used in A operations. Registers 232-7, 232-8, 232-9, 232-10, and 232-11 can define the size of outputs of A operations, the number of outputs in AI operations, and the start address and end address of the outputs of AI operations.

Register 232-12 can be used to enable the usage of the input blocks, the neuron blocks, the output blocks, the bias blocks, the activation functions, and the temporary blocks used during A operations.

Registers 232-13, 232-14, 232-15, 232-16, 232-17, 232-18, 232-19, 232-20, 232-21, 232-22, 232-23, 232-24, and 232-25 can be used to define the neural network used during AI operations. Registers 232-13, 232-14, 232-15, 232-16, 232-17, 232-18, 232-19, 232-20, 232-21, 232-22, 232-23, 232-24, and 232-25 can define the size, number, and location of neurons and/or layers of the neural network used during AI operations.

Register 232-26 can enable a debug/hold mode of the A accelerator and output to be observed at a layer of A operations. For example, a controller can be configured to perform an AI operation on data stored in a number of memory arrays, stop the AI operation, and perform a debug operation on the A operation.

Register 232-26 can indicate that an activation should be applied during AI operations and that the AI operation can step forward (e.g., perform a next step in an AI operation) in AI operations. The controller can enable the AI accelerator to perform the debug operation on the AI operation by programming a bit and/or bits of register 232-26 to a particular state. In some examples, the first bit of register 232-26 can be programmed to a first state to start the debug operation and programmed to a second state to stop and/or prevent the debug operation. The controller can program the bits and/or bits of register 232-26 to a particular state in response to receiving a command from the host, for example.

Register 232-26 can indicate that that the AI operation can step forward (e.g., perform a next step in an AI operation) in AI operations. In some examples, a second bit of register 232-26 can be programmed to a first state to indicate that the AI operation can step forward in AI operations and to a second state to indicate that the A operation cannot step forward.

Register 232-26 can indicate that the temporary blocks, where the output of the layer is located, are valid. The temporary blocks can be read by the host in response to the temporary blocks being indicated as valid by register 232-26. A third bit of register 232-26 can be programmed to a first state to indicate the temporary blocks are valid and to a second state to indicate the temporary blocks are invalid.

Debug operations can include storing data (e.g., errors and/or results from the AI operations) in the temporary blocks of the number of memory arrays and validating the data. For example, a fourth bit of register 232-26 can be programmed to a first state to store the errors from the A operations for correction. In some examples, when the fourth bit of register 232-26 is programmed to a second state, there are no errors stored. The data in the temporary blocks can be changed by a host and/or a controller on the memory device (e.g., to correct errors in data), such that the changed data can be used in the A operation as the A operation steps forward.

The result of the debug operation can be stored and/or transmitted. For example, the result of the debug operation can be stored in a different block in the number of memory arrays and/or sent to a host. A fifth bit of register 232-26 can be programmed to a first state to send the result of the debug operation to the host and a sixth bit of register 232-26 can be programmed to a first state to store the result of the debug operation in a different block in the number of memory arrays.

Registers 232-27, 232-28, and 232-29 can define the layer where the debug/hold mode will stop the AI operation, change content of a neural network, change an input value, change a bias value, change an activation function, observe the output of the layer, and/or send the output of the layer. In some examples, the registers 232-27, 232-28, and 232-29 can define layers where errors consistently occur and/or layers where the neural network has been changed. Registers 232-30, 232-31, 232-32, and 232-33 can define the size of temporary blocks used in AI operations and the start address and end address of the temporary blocks used in AI operations. Register 232-30 can define the start address and end address of a first temporary block used in AI operations and register 232-33 can define the start address and end address of a first temporary block used in A operations. Registers 232-31, and 232-32 can define the size of the temporary blocks used in AI operations.

Registers 232-34, 232-35, 232-36, 232-37, 232-38, and 232-39 can be associated with the activation functions used in A operations. Register 232-34 can enable usage of the activation function block, enable usage of the activation function for each neuron, the activation function for each layer, and enables usage of an external activation function. Registers 232-35 can define the start address and the end address of the location of the activation functions. Registers 232-36, 232-37, 232-38, and 232-39 can define the resolution of the inputs (e.g., x-axis) and outputs (e.g., y-axis) of the activation functions.

Registers 232-40, 232-41, 232-42, 232-43, and 232-44 can define the size of bias values used in AI operations, the number of bias values used in AI operations, and the start address and end address of the bias values used in AI operations.

Register 232-45 can provide status information for the AI calculations and provide information for the debug/hold mode. Register 232-45 can enable debug/hold mode, indicate that the AI accelerator is performing AI operations, indicate that the full capability of the A accelerator should be used, indicate only matrix calculations of the AI operations should be made, and/or indicate that the AI operation can proceed to the next neuron and/or layer.

Register 232-46 can provide error information regarding AI operations. Register 232-46 can indicate that there was an error in a sequence of an AI operation, that there was an error in an algorithm of an A operations, that there was an error in a page of data that ECC was not able to correct, and/or that there was an error in a page of data that ECC was able to correct.

Register 232-47 can indicate an activation function to use in AI operations. Register 232-47 can indicated one of a number of pre-define activation function can be used in A operations and/or a custom activation function located in a block can be used in A operations.

Registers 232-48, 232-49, and 232-50 can indicate the neuron and/or layer where the AI operation is executing. In the case where errors occur during the AI operations, registers 232-48, 232-49, and 232-50 can store the location of the neuron and/or layer where an error occurred.

FIGS. 3A and 3B are block diagrams of a number of bits in a number of registers on a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure. Each register 332-0, . . . , 332-50 can include a number of bits, bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7, to indicate information associated with performing AI operations. The number of registers can include 8 bits to store the information associated with performing the AI operations; however, the number of registers can include any number of bits based on a size of the memory including the AI accelerator.

Register 332-0 can define parameters associated with AI mode of the memory device. Bit 334-5 of register 332-0 can be a read/write bit and can indicate that an elaboration of an AI operation can restart 360 at the beginning when programmed to 1b, for example, although other programming conventions can be used. Bit 334-5 of register 332-0 can be reset to 0b once the A operation has restarted. Bit 334-4 of register 332-0 can be a read/write bit and can indicate that an elaboration of an AI operation can start 361 when programmed to 1b. Bit 334-4 of register 332-0 can be reset to 0b once the A operation has started.

Bit 334-3 of register 332-0 can be a read/write bit and can indicate that the content of the AI registers is valid 362 when programmed to 1b and invalid when programmed to 0b. Bit 334-2 of register 332-0 can be a read/write bit and can indicate that the content of the AI registers is to be cleared 363 when programmed to 1b. Bit 334-1 of register 332-0 can be a read only bit and can indicate that the AI accelerator is in use 363 and performing AI operations when programmed to 1b. Bit 334-0 of register 332-0 can be a write only bit and can indicate that the memory device is to exit 365 AI mode when programmed to 1b.

Registers 332-1, 332-2, 332-3, 332-4, and 332-5 can define the size of inputs used in AI operations, the number of inputs used in A operations, and the start address and end address of the inputs used in A operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-1 and 332-2 can define the size of the inputs 366 used in AI operations. The size of the inputs can indicate the width of the inputs in terms of number of bits and/or the type of input, such as floating point, integer, and/or double, among other types. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-3 and 332-4 can indicate the number of inputs 367 used in AI operations. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-5 can indicate a start address 368 of the blocks in memory arrays of the inputs used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-5 can indicate an end address 369 of the blocks in memory arrays of the inputs used in AI operations. If the start address 368 and the end address 369 is the same address, only one block of input is indicated for the A operations.

Registers 332-7, 332-8, 332-9, 332-10, and 332-11 can define the size of outputs of AI operations, the number of outputs in A operations, and the start address and end address of the outputs of A operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-7 and 332-8 can define the size 370 of the outputs used in AI operations. The size of the outputs can indicate the width of the outputs in terms of number of bits and/or the type of output, such as floating point, integer, and/or double, among other types. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-9 and 332-10 can indicate the number of outputs 371 used in A operations. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-11 can indicate a start address 372 of the blocks in memory arrays of the outputs used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-11 can indicate an end address 373 of the blocks in memory arrays of the outputs used in AI operations. If the start address 372 and the end address 373 is the same address, only one block of output is indicated for the AI operations.

Register 332-12 can be used to enable the usage of the input blocks, the neuron blocks, the output blocks, the bias blocks, the activation functions, and the temporary blocks used during AI operations. Bit 334-0 of register 332-12 can enable the input blocks 380, bit 334-1 of register 332-12 can enable the neural network blocks 379, bit 334-2 of register 332-12 can enable the output blocks 378, bit 334-3 of register 332-12 can enable the bias blocks 377, bit 334-4 of register 332-12 can enable the activation function blocks 376, and bit 334-5 and 334-6 of register 332-12 can enable a first temporary 375 block and a second temporary block 374.

Registers 332-13, 332-14, 332-15, 332-16, 332-17, 332-18, 332-19, 332-20, 332-21, 332-22, 332-23, 332-24, and 332-25 can be used to define the neural network used during AI operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-13 and 332-14 can define the number of rows 381 in a matrix used in A operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-15 and 332-16 can define the number of columns 382 in a matrix used in A operations.

Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-17 and 332-18 can define the size of the neurons 383 used in AI operations. The size of the neurons can indicate the width of the neurons in terms of number of bits and/or the type of input, such as floating point, integer, and/or double, among other types. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-19, 332-20, and 322-21 can indicate the number of neurons 384 of the neural network used in AI operations. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-22 can indicate a start address 385 of the blocks in memory arrays of the neurons used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-5 can indicate an end address 386 of the blocks in memory arrays of the neurons used in AI operations. If the start address 385 and the end address 386 is the same address, only one block of neurons is indicated for the AI operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-23, 332-24, and 322-25 can indicate the number of layers 387 of the neural network used in AI operations.

Register 332-26 can enable a debug/hold mode of the A accelerator and an output to be observed at a layer of A operations. For example, a controller can be configured to perform AI operations on data stored in a number of memory arrays, stop the AI operations, and perform debug operations on the A operations.

The controller can indicate that the AI accelerator is in a debug/hold mode by programming a bit and/or bits of register 332-26 to particular states. Bit 334-0 of register 332-26 can indicate that the AI accelerator is in a debug/hold mode and that an activation function should be applied 391 during AI operations. In some examples, bit 334-0 can be programmed to a first state to start the debug operations and programmed to a second state to stop and/or prevent debug operations from occurring. The controller can program bit 334-0 to the first state and/or second state in response to receiving a command from the host, for example.

Bit 334-1 of register 332-26 can indicate that the AI operation can step forward 390 (e.g., perform a next step in an AI operation) in AI operations. In some examples, bit 334-1 can be programmed to a first state to indicate that the AI operation can step forward 390 in AI operations and to a second state to indicate that the AI operation cannot step forward. The programming of bit 334-1 can be embedded in the execution of the AI operations. The A operations can be stopped, results of the AI operations can be observed, errors can be corrected, and/or the register 332-26 can be reprogrammed to include another step and/or remove a step in the AI operations. In some examples, previous content at a particular step of the AI operations can restore temporary content to see an effect of a modification on the AI operations.

Bit 334-2 and bit 334-3 of register 232-26 can indicate that the temporary blocks, where the output of the layer is located, is valid 388 and 389. For example, bit 334-2 and bit 334-3 of register 232-26 can be programmed to a first state to indicate the temporary blocks are valid 388 and 389 and programmed to a second state to indicate the temporary blocks are invalid. In some examples, indicating a temporary block is invalid signals to the host and/or controller that data should not be read from the temporary block. The data in the temporary blocks can be changed by a host and/or a controller on the memory device, such that the changed data can be used in the A operation as the A operation steps forward.

The result of the debug operations can be stored and/or transmitted. For example, the result of the debug operations can be stored in a different block in the number of memory arrays and/or sent to a host. In some examples, one or more of bits 334-4, . . . , 334-7 can be programmed to a first state to send the result of the debug operations to the host and one or more of bits 334-4, . . . , 334-7 can be programmed to a first state to store the result of the debug operations in a different block in the number of memory arrays.

Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-27, 332-28, and 332-29 can define the layer where the debug/hold mode will stop 392 the AI operation and observe the output of the layer.

Registers 332-30, 332-31, 332-32, and 332-33 can define the size of temporary blocks used in AI operations and the start address and end address of the temporary blocks used in AI operations. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-30 can define the start address 393 of a first temporary block used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-30 can define the end address 394 of a first temporary block used in A operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-31 and 332-32 can define the size 395 of the temporary blocks used in AI operations. The size of the temporary blocks can indicate the width of the temporary blocks in terms of number of bits and/or the type of input, such as floating point, integer, and/or double, among other types. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-33 can define the start address 396 of a second temporary block used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-34 can define the end address 397 of a second temporary block used in AI operations.

Registers 332-34, 332-35, 332-36, 332-37, 332-38, and 332-39 can be associated with the activation functions used in AI operations. Bit 334-0 of register 332-34 can enable usage of the activation function block 3101. Bit 334-1 of register 332-34 can enable holding that AI at a neuron 3100 and usage of the activation function for each neuron. Bit 334-2 of register 332-34 can enable holding the AI at a layer 399 and the usage of the activation function for each layer. Bit 334-3 of register 332-34 can enable usage of an external activation function 398.

Bits 334-4, 334-5, 334-6, and 334-7 of register 332-35 can define the start address 3102 of activation function blocks used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-35 can define the end address 3103 of activation functions blocks used in AI operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-36 and 332-37 can define the resolution of the inputs (e.g., x-axis) 3104 of the activation functions. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-38 and 332-39 can define the resolution of the outputs (e.g., y-axis) 3105 of the activation functions for a given x-axis value of a custom activation function.

Registers 332-40, 332-41, 332-42, 332-43, and 332-44 can define the size of bias values used in AI operations, the number of bias values used in AI operations, and the start address and end address of the bias values used in AI operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-40 and 332-41 can define the size of the bias values 3106 used in AI operations. The size of the bias values can indicate the width of the bias values in terms of number of bits and/or the type of bias values, such as floating point, integer, and/or double, among other types. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-42 and 332-43 can indicate the number of bias values 3107 used in AI operations. Bits 334-4, 334-5, 334-6, and 334-7 of register 332-44 can indicate a start address 3108 of the blocks in memory arrays of the bias values used in AI operations. Bits 334-0, 334-1, 334-2, and 334-3 of register 332-44 can indicate an end address 3109 of the blocks in memory arrays of the bias values used in AI operations. If the start address 3108 and the end address 3109 is the same address, only one block of bias values is indicated for the AI operations.

Register 332-45 can provide status information for the AI calculations and provide information for the debug/hold mode. Bit 334-0 of register 332-45 can activate the debug/hold mode 3114. Bit 334-1 of register can indicate that the AI accelerator is busy 3113 and performing AI operations. Bit 334-2 of register 332-45 can indicate that the AI accelerator is on 3112 and/or that the full capability of the AI accelerator should be used. Bit 334-3 of register 332-45 can indicate only matrix calculations 3111 of the AI operations should be made. Bit. 334-4 of register 332-45 can indicate that the AI operation can step forward 3110 and proceed to the next neuron and/or layer.

Register 332-46 can provide error information regarding AI operations. The host can retrieve A operation information when AI operations are being performed. Bit 334-3 of register 332-46 can indicate that there was an error in a sequence 3115 of an AI operation. Bit 334-2 of register 332-46 can indicate that there was an error in an algorithm 3116 of an AI operation. Bit 334-1 of register 332-46 can indicate there was an error in a page of data that ECC was not able to correct 3117. Bit 334-0 of register 332-46 can indicate there was an error in a page of data that ECC was able to correct 3118.

Register 332-47 can indicate an activation function to use in AI operations. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, and 334-6 of register 332-47 can indicate one of a number of pre-define activation functions 3120 can be used in AI operations. Bit 334-7 of register 332-47 can indicate a custom activation function 3119 located in a block can be used in A operations.

Registers 332-48, 332-49, and 332-50 can indicate the neuron and/or layer where the AI operation is executing. Bits 334-0, 334-1, 334-2, 334-3, 334-4, 334-5, 334-6, and 334-7 of registers 332-48, 332-49, and 332-50 can indicate the address of the neuron and/or layer where the AI operation is executing. In the case where errors occur during the A operations, registers 332-48, 332-49, and 332-50 can indicate the neuron and/or layer where an error occurred.

FIG. 4 is a block diagram of a number of blocks of a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure. Input block 440 is a block in the memory arrays where input data is stored. Data in input block 440 can be used as the input for AI operations. The address of input block 440 can be indicated in register 5 (e.g. register 232-5 in FIGS. 2 and 332-5 in FIG. 3A). Embodiments are not limited to one input block as there can be a plurality of input blocks. Data input block 440 can be sent to the memory device from the host. The data can accompany a command indicated that AI operations should be performed on the memory device using the data.

Output block 420 is a block in the memory arrays where output data from AI operations is stored. Data in output block 442 can be used store the output from AI operations and sent to the host. The address of output block 442 can be indicated in register 11 (e.g. register 232-11 in FIGS. 2 and 332-11 in FIG. 3A). Embodiments are not limited to one output block as there can be a plurality of output blocks.

Data in output block 442 can be sent to host upon completion and/or holding of an AI operation. Temporary blocks 444-1 and 444-2 can be blocks in memory arrays where data is stored temporarily while AI operations are being performed. Although FIG. 4 includes two temporary blocks 444-1 and 444-2, the memory device can include one or more temporary blocks. Data can be stored in temporary blocks 444-1 and 444-2 while the AI operations are iterating through the neuron and layers of the neural network used for the AI operations. The address of temporary block 448 can be indicated in registers 30 and 33 (e.g. registers 232-30 and 232-33 in FIGS. 2 and 332-30 and 332-33 in FIG. 3B). Embodiments are not limited to two temporary blocks as there can be a plurality of temporary blocks.

Activation function block 446 can be a block stored in the memory array where the activation functions for the AI operations are stored and/or in the memory controller firmware. Activation function block 446 can store pre-defined activation functions and/or custom activation functions that are created by the host and/or AI accelerator. The address of activation function block 448 can be indicated in register 35 (e.g. register 232-35 in FIGS. 2 and 332-35 in FIG. 3B). Embodiments are not limited to one activation function block as there can be a plurality of activation function blocks.

Bias values block 448 is a block in the memory array where the bias values for the AI operations are stored. The address of bias values block 448 can be indicated in register 44 (e.g. register 232-44 in FIGS. 2 and 332-44 in FIG. 3B). Embodiments are not limited to one bias value block as there can be a plurality of bias value blocks.

Neural network blocks 450-1, 450-2, 450-3, 450-4, 450-5, 450-6, 450-7, 450-8, 450-9, and 450-10 are a block in the memory array where the neural network for the AI operations are stored. Neural network blocks 450-1, 450-2, 450-3, 450-4, 450-5, 450-6, 450-7, 450-8, 450-9, and 450-10 can store the information for the neurons and layers that are used in the A operations. The address of neural network blocks 450-1, 450-2, 450-3, 450-4, 450-5, 450-6, 450-7, 450-8, 450-9, and 450-10 can be indicated in register 22 (e.g. register 232-22 in FIGS. 2 and 332-22 in FIG. 3A).

FIG. 5 is a flow diagram illustrating an example artificial intelligence process in a memory device with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure. In response to starting an AI operation, an A accelerator can write input data 540 and neural network data 550 to the input and neural network block, respectively. The AI accelerator can perform AI operations using input data 540 and neural network data 550. The results can be stored in temporary blocks 544-1 and 544-2. The temporary blocks 554-1 and 544-2 can be used to store data while performing matrix calculations, adding bias data, and/or to apply activation functions during the AI operations.

An AI accelerator can receive the partial results of A operations stored in temporary blocks 544-1 and 544-2 and bias value data 548 and perform AI operations using the partial results of AI operations bias value data 548. The results can be stored in temporary blocks 544-1 and 544-2.

An AI accelerator can receive the partial results of A operations stored in temporary blocks 544-1 and 544-2 and activation function data 546 and perform AI operations using the partial results of A operations and activation function data 546. The results can be stored in output blocks 542.

A controller can be configured to perform AI operations on data stored in a number of memory arrays, stop the A operations, and perform a debug operation on the AI operations. Debug operations 552, 554, 556 can occur after the AI accelerator performs AI operations using input data 540 and neural network data 550, after performing AI operations using the partial results of AI operations bias value data 548, and/or after performing AI operations using the partial results of AI operations and activation function data 546.

The controller can enable the apparatus to perform the debug operations on the AI operations by programming a bit and/or bits of a register to a particular state. In some examples, the first bit of a register can be programmed to a first state to start the debug operations and programmed to a second state to stop and/or prevent the debug operations. The controller can program the bits and/or bits of the register to a particular state in response to receiving a command from the host, for example.

A register can indicate that that the AI operation can step forward (e.g., perform a next step in an AI operation) in AI operations. In some examples, a second bit can be programmed to a first state to indicate that the A operation can step forward in AI operations and to a second state to indicate that the A operation cannot step forward.

The register can indicate that the temporary blocks, where the output of the layer is located, are valid. A third bit and/or a fourth bit of the register can be programmed to a first state to indicate the temporary blocks are valid and to a second state to indicate the temporary blocks are invalid.

Debug operations can include storing data from the AI operations in the temporary blocks of the number of memory arrays and validating the temporary blocks. The data (e.g., partial results from the AI operations, errors from the AI operations, and/or a neural network, activation functions, input values, and/or bias values) in the temporary blocks can be changed by a host and/or a controller on the memory device, such that the changed data can be used in the AI operation as the AI operation steps forward.

The debug operation result can also be stored in temporary blocks 544-1 and/or 544-2. The result of the debug operations, partial results from the AI operations, errors from the AI operations, and/or a neural network, activation functions, input values, and/or bias values can be stored and/or transmitted. For example, the result of the debug operation can be stored in output block 542 in the number of memory arrays and/or sent to a host. A fifth bit of the register can be programmed to a first state to send the result of the debug operations to the host and a sixth bit can be programmed to a first state to store the result of the debug operations in the output block.

FIG. 6A is a block diagram of an apparatus in the form of a computing system 600 including a memory device 620 with an artificial intelligence (AI) accelerator, which includes a memory array 625 in accordance with a number of embodiments of the present disclosure. As used herein, a memory device 620, controller 640, memory array 625, sensing circuitry 6138, and/or a number of additional latches 6140 might also be separately considered an “apparatus.”

In FIG. 6A, the AI accelerator (e.g., AI accelerator 124 in FIG. 1) can include sensing circuitry 6138 and additional latches 6140, among other components described in association with FIGS. 6A-8B, that are configured to perform operations, such as logic operations, associated with AI operations. As described below in associated with FIGS. 6A-9B, memory devices (e.g., memory device 620) can be configured to perform operations associated with A operations as part of the A accelerator.

As used herein, the additional latches are intended to mean additional functionalities (e.g., amplifiers, select logic) that sense, couple, and/or move (e.g., read, store, cache) data values of memory cells in an array and that are distinct from the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 shown in FIGS. 6B, 7, 8, 9A and 9B. The logic stripes 6152-1, . . . , 6152-N in a data path of a plurality of shared input/output (I/O) lines 6144 local to the array, as shown in FIGS. 6A and 6B, may be associated with various bank sections 6150-1, . . . , 6150-N of memory cells in the bank 6146-1. The bank 6146-1 may be one of a plurality of banks on the memory device 620.

System 600 in FIG. 6A includes a host 602 coupled (e.g., connected) to the memory device 620. Host 602 can be a host system such as a personal laptop computer, a desktop computer, a digital camera, a smart phone, or a memory card reader, among various other types of hosts. Host 602 can include a system motherboard and/or backplane and can include a number of processing resources (e.g., one or more processors, microprocessors, or some other type of controlling circuitry). The system 600 can include separate integrated circuits or both the host 602 and the memory device 620 can be on the same integrated circuit. The system 600 can be, for instance, a server system and/or a high performance computing (HPC) system and/or a portion thereof. Although the examples shown in FIG. 6A illustrates a system having a Von Neumann architecture, embodiments of the present disclosure can be implemented in non-Von Neumann architectures, which may not include one or more components (e.g., CPU, ALU, etc.) often associated with a Von Neumann architecture.

For clarity, the system 600 has been simplified to focus on features with particular relevance to the present disclosure. The memory array 625 can be a DRAM array, SRAM array, STT RAM array, PCRAM array, TRAM array, RRAM array, NAND flash array, and/or NOR flash array, among other types of arrays. The array 625 can include memory cells arranged in rows coupled by access lines (which may be referred to herein as word lines or select lines) and columns coupled by sense lines (which may be referred to herein as data lines or digit lines). Although a single array 625 is shown in FIG. 6A, embodiments are not so limited. For instance, memory device 620 may include a number of arrays 625 (e.g., a number of banks of DRAM cells, NAND flash cells, etc.).

The memory device 620 can include address circuitry 6525 to latch address signals provided over a data bus 656 (e.g., an I/O bus connected to the host 602) by I/O circuitry 6134 (e.g., provided to external ALU circuitry and/or to DRAM DQs via local I/O lines and global I/O lines). As used herein, DRAM DQs can enable input of data to and/or output of data from a bank (e.g., from and/or to the controller 640 and/or host 602) via a bus (e.g., data bus 656). During a write operation, a voltage (high=1, low=0) can be applied to a DQ (e.g., a pin). This voltage can be translated into an appropriate signal and stored in a selected memory cell. During a read operation, a data value read from a selected memory cell can appear at the DQ once access is complete and the output is enabled (e.g., by the output enable signal being low). At other times, DQs can be in a high impedance state, such that the DQs do not source or sink current and do not present a signal to the system. This also may reduce DQ contention when two or more devices (e.g., banks) share a combined data bus, as described herein. Such DQs are separate and distinct from the plurality of shared I/O lines 6144 (in FIG. 1AB) in a data path local to the array 625.

Status and exception information can be provided from the controller 640 of the memory device 620 to a channel controller 604, for example, through an out-of-band (OOB) bus 657, e.g., high-speed interface (HSI), which in turn can be provided from the channel controller 604 to the host 602. The channel controller 604 can include a logic component to allocate a plurality of locations (e.g., controllers for subarrays) in the arrays of each respective bank to store bank commands, application instructions (e.g., for sequences of operations), and arguments (PIM commands) for various banks associated with operations for each of a plurality of memory devices 620. The channel controller 604 can dispatch commands (e.g., PIM commands) to the plurality of memory devices 620 to store those program instructions within a given bank 6146 (FIG. 6B) of a memory device 620.

Address signals are received through address circuitry 6525 and decoded by a row decoder 6132 and a column decoder 6142 to access the memory array 625. Data can be sensed (read) from memory array 625 by sensing voltage and/or current changes on sense lines (digit lines) using a number of sense amplifiers, as described herein, of the sensing circuitry 6138. A sense amplifier can read and latch a page (e.g., a row) of data from the memory array 625. Additional compute circuitry, as described herein, can be coupled to the sensing circuitry 6138 and can be used in combination with the sense amplifiers to sense, store (e.g., cache and/or buffer), perform compute functions (e.g., operations), and/or move data. The I/O circuitry 6134 can be used for bi-directional data communication with host 602 over the data bus 656 (e.g., a 64 bit wide data bus). The write circuitry 6136 can be used to write data to the memory array 625.

Controller 640 (e.g., bank control logic, sequencer and timing circuitry shown in FIG. 6A) can decode signals (e.g., commands) provided by control bus 654 from the host 602. These signals can include chip enable signals, write enable signals, and/or address latch signals that can be used to control operations performed on the memory array 625, including data sense, data store, data movement (e.g., copying, transferring, and/or transporting data values), data write, and/or data erase operations, among other operations. In various embodiments, the controller 640 can be responsible for executing instructions from the host 602 and accessing the memory array 625. The controller 640 can be a state machine, a sequencer, or some other type of controller. The controller 640 can control shifting data (e.g., right or left) in a row of an array (e.g., memory array 625) and execute microcode instructions to perform operations such as compute operations, e.g., AND, OR, NOR, XOR, add, subtract, multiply, divide, etc.

Examples of the sensing circuitry 6138 are described further below (e.g., in FIGS. 6A-9B). For instance, in some embodiments, the sensing circuitry 6138 can include a number of sense amplifiers and a number of compute components, which may serve as an accumulator and can be used to perform operations in each subarray (e.g., on data associated with complementary sense lines).

In some embodiments, the sensing circuitry 6138 can be used to perform operations using data stored in memory array 625 as inputs and participate in movement of the data for copy, transfer, transport, writing, logic, and/or storage operations to a different location in the memory array 625 without transferring the data via a sense line address access (e.g., without firing a column decode signal). As such, various compute functions can be performed using, and within, sensing circuitry 6138 rather than (or in association with) being performed by processing resources external to the sensing circuitry 6138 (e.g., by a processor associated with host 602 and/or other processing circuitry, such as ALU circuitry, located on device 620, such as on controller 640 or elsewhere). However, in addition, embodiments according to the present disclosure perform compute functions on data values moved to a plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit from the rows of the array. And as an example, according to embodiments, compute operations may be controlled in the compute unit at speeds of 2 nanoseconds (ns) without having to move the data values back into the rows, as compared to an example time required to fire the rows in the array of 60 nanoseconds (ns).

In various previous approaches, data associated with an operand, for instance, would be read from memory via sensing circuitry and provided to external ALU circuitry via I/O lines (e.g., via local I/O lines and/or global I/O lines). The external ALU circuitry could include a number of registers and would perform compute functions using the operands, and the result would be transferred back to the array via the I/O circuitry 6134.

In contrast, embodiments according to the present disclosure perform compute functions on data values, moved to a plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N via a plurality of shared I/O lines 6144 from the rows of the array, in a compute unit in a data path local to the array. Additionally, sensing circuitry 6138 may be configured to perform operations on data stored in memory array 625 and store the result back to the memory array 625 without enabling an I/O line (e.g., a local I/O line) coupled to the sensing circuitry 6138. However, once loaded, compute operations may be controlled in the compute unit much faster, e.g., at speeds of 2 nanoseconds (ns), without having to move the data values back into the rows, as compared to an example time required to fire the rows in the array, e.g., 60 nanoseconds (ns). The sensing circuitry 6138 can be formed on pitch with the memory cells of the array. The plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N, associated with the data path of the plurality of shared I/O lines 6144, have a pitch equal to that of the data path and that is a function of a pitch of digit lines to the array of memory cells. For example, the compute component has a pitch that is an integer multiple of the pitch of digit lines to the array of memory cells.

For example, the sensing circuitry 6138 described herein can be formed on a same pitch as a pair of complementary sense lines (e.g., digit lines). As an example, a pair of complementary memory cells may have a cell size with a 6F² pitch (e.g., 3F×2F), where F is a feature size. If the pitch of a pair of complementary sense lines for the complementary memory cells is 3F, then the sensing circuitry being on pitch indicates the sensing circuitry (e.g., a sense amplifier and corresponding compute component per respective pair of complementary sense lines) is formed to fit within the 3F pitch of the complementary sense lines. Likewise, the compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N, associated with the data path of the plurality of shared I/O lines 6144, have a pitch that is a function of the 3F pitch of the complementary sense lines. For example, the compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N will have a pitch that is an integer multiple of the 3F pitch of digit lines to the array of memory cells.

By contrast, the circuitry of the processing resource(s) (e.g., a compute engine, such as an ALU) of various prior systems may not conform to pitch rules associated with a memory array. For example, the memory cells of a memory array may have a 4F² or 6F² cell size. As such, the devices (e.g., logic gates) associated with ALU circuitry of previous systems may not be capable of being formed on pitch with the memory cells (e.g., on a same pitch as the sense lines), which can affect chip size and/or memory density, for example. In the context of some computing systems and subsystems (e.g., a central processing unit (CPU)), data may be processed in a location that is not on pitch and/or on chip with memory (e.g., memory cells in the array), as described herein. For example, the data may be processed by a processing resource associated with a host, for instance, rather than on pitch with the memory.

As such, in a number of embodiments, circuitry external to array 625 and sensing circuitry 6138 is not needed to perform compute functions as the sensing circuitry 6138 can perform the appropriate operations to perform such compute functions or can perform such operations in a data path of a plurality of shared I/O lines local to the array without the use of an external processing resource. Therefore, the sensing circuitry 6138 and/or the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 may be used to complement or to replace, at least to some extent, such an external processing resource (or at least the bandwidth consumption of such an external processing resource). In some embodiments, the sensing circuitry 6138 and/or the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 may be used to perform operations (e.g., to execute instructions) in addition to operations performed by an external processing resource (e.g., host 602). For instance, host 602 and/or sensing circuitry 6138 may be limited to performing only certain operations and/or a certain number of operations.

Operations described herein can include operations associated with a processing in memory (PIM) capable device. PIM capable device operations can use bit vector based operations. As used herein, the term “bit vector” is intended to mean a physically contiguous number of bits on a bit vector memory device (e.g., a PIM device) stored physically contiguous in a row of an array of memory cells. Thus, as used herein a “bit vector operation” is intended to mean an operation that is performed on a bit vector that is a contiguous portion of virtual address space (e.g., used by a PIM device). For example, a row of virtual address space in the PIM device may have a bit length of 16K bits (e.g., corresponding to 16K complementary pairs of memory cells in a DRAM configuration). Sensing circuitry 6138, as described herein, for such a 16K bit row may include a corresponding 16K processing elements (e.g., compute components, as described herein) formed on pitch with the sense lines selectably coupled to corresponding memory cells in the 16 bit row. A compute component in the PIM device may operate as a one bit processing element (PE) on a single bit of the bit vector of the row of memory cells sensed by the sensing circuitry 6138 (e.g., sensed by and/or stored in a sense amplifier paired with the compute component, as described herein). Similarly, the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 may operate as a one bit processing element (PE) on a single bit of the bit vector of the row of memory cells sensed in an array.

Enabling an I/O line can include enabling (e.g., turning on, activating) a transistor having a gate coupled to a decode signal (e.g., a column decode signal) and a source/drain coupled to the I/O line. However, embodiments are not limited to not enabling an I/O line. For instance, in a number of embodiments, the sensing circuitry (e.g., 6138) can be used to perform operations without enabling column decode lines of the array.

However, the plurality of shared I/O lines 6144 may be enabled in order to load data values to the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 where compute operations may be controlled much faster. For example, in the plurality of compute components 6148-1, . . . , 6148-M and/or logic stripes 6152-1, . . . , 6152-N in the compute unit, the compute operation may be performed at speeds of 2 nanoseconds (ns). This enhancement of speed can be attributed to not having to move the data values back into the rows with the associated time used in firing the rows in the array, e.g., 60 nanoseconds (ns).

FIG. 6B is block diagram of an apparatus in the form of a computing system including a memory device having a shared input/out (I/O) line in a data path local to bank sections of an array with an artificial intelligence (AI) accelerator in accordance with a number of embodiments of the present disclosure. For example, bank 6146-1 can represent an example bank of a memory device 620. As shown in FIG. 6B, a bank 6146-1 can include a plurality of main memory columns (shown horizontally as X) (e.g., 16,384 columns in an example DRAM bank). Additionally, the bank 6146-1 may be divided up into bank sections (e.g., quadrants of 32 subarrays), 6150-1, 6150-2, . . . , 6150-N. Each bank section may be associated with a plurality of compute components 6148-1, . . . , 6148-M in logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144. Each of the of the bank sections 6150-1, . . . , 6150-N can include a plurality of rows (shown vertically as Y) (e.g., each section may be a quadrant that includes 32 subarrays that each may include 512 rows in an example DRAM bank). Example embodiments are not limited to the example horizontal and/or vertical orientation of columns and rows described here or the example numbers thereof.

As shown in FIG. 6B, the bank 6146-1 can be divided into a plurality of bank sections 6150-1, . . . , 6150-N. Each bank sections can have a plurality of compute components 6148-1, . . . , 6148-M and logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144 associated therewith. The bank 6146-1 can include a controller 640 to direct operations on data values loaded to the plurality of compute components 6148-1, . . . , 6148-M in logic stripes 6152-1, . . . , 6152-N in a compute unit in a data path of the plurality of shared I/O lines 6144.

FIG. 7 is a schematic diagram illustrating sensing circuitry 7138 in accordance with a number of embodiments of the present disclosure. The sensing circuitry 7138 can correspond to sensing circuitry 6138 shown in FIG. 6A.

As shown in the example embodiment of FIG. 7, a memory cell can include a storage element (e.g., capacitor) and an access device (e.g., transistor). For example, a first memory cell can include transistor 7160-1 and capacitor 7162-1, and a second memory cell can include transistor 7160-2 and capacitor 7162-2, etc. In this embodiment, the memory array 725 is a DRAM array of 1T1B (one transistor one capacitor) memory cells, although other embodiments of configurations can be used (e.g., 2T2C with two transistors and two capacitors per memory cell). In a number of embodiments, the memory cells may be destructive read memory cells (e.g., reading the data stored in the cell destroys the data such that the data originally stored in the cell is refreshed after being read).

The cells of the memory array 725 can be arranged in rows coupled by access (word) lines 7164-X (Row X), 7164-Y (Row Y), etc., and columns coupled by pairs of complementary sense lines (e.g., digit lines DIGIT(D) and DIGIT(D)_shown in FIG. 7). The individual sense lines corresponding to each pair of complementary sense lines can also be referred to as digit lines 7168-1 for DIGIT (D) and 7168-2 for DIGIT (D)_, respectively, or corresponding reference numbers in FIGS. 8 and 9A-9B. Although only one pair of complementary digit lines are shown in FIG. 7, embodiments of the present disclosure are not so limited, and an array of memory cells can include additional columns of memory cells and digit lines (e.g., 4,096, 8,192, 16,384, etc.).

Although rows and columns are illustrated as orthogonally oriented in a plane, embodiments are not so limited. For example, the rows and columns may be oriented relative to each other in any feasible three-dimensional configuration. For example, the rows and columns may be oriented at any angle relative to each other, may be oriented in a substantially horizontal plane or a substantially vertical plane, and/or may be oriented in a folded topology, among other possible three-dimensional configurations.

Memory cells can be coupled to different digit lines and word lines. For example, a first source/drain region of a transistor 7160-1 can be coupled to digit line 7168-1 (D), a second source/drain region of transistor 7160-1 can be coupled to capacitor 7162-1, and a gate of a transistor 7160-1 can be coupled to word line 7164-Y. A first source/drain region of a transistor 7160-2 can be coupled to digit line 7168-2 (D)_, a second source/drain region of transistor 7160-2 can be coupled to capacitor 7162-2, and a gate of a transistor 7160-2 can be coupled to word line 7164-X. A cell plate, as shown in FIG. 7, can be coupled to each of capacitors 7162-1 and 7162-2. The cell plate can be a common node to which a reference voltage (e.g., ground) can be applied in various memory array configurations.

The memory array 725 is configured to couple to sensing circuitry 7138 in accordance with a number of embodiments of the present disclosure. In this embodiment, the sensing circuitry 7138 comprises a sense amplifier 7170 and a compute component 7148 corresponding to respective columns of memory cells (e.g., coupled to respective pairs of complementary digit lines). The sense amplifier 7170 can be coupled to the pair of complementary digit lines 7168-1 and 7168-2. The compute component 7148 can be coupled to the sense amplifier 7170 via pass gates 7172-1 and 7172-2. The gates of the pass gates 7172-1 and 7172-2 can be coupled to operation selection logic 7178.

The operation selection logic 7178 can be configured to include pass gate logic for controlling pass gates that couple the pair of complementary digit lines un-transposed between the sense amplifier 7170 and the compute component 7148 and swap gate logic for controlling swap gates that couple the pair of complementary digit lines transposed between the sense amplifier 7170 and the compute component 7148. The operation selection logic 7178 can also be coupled to the pair of complementary digit lines 7168-1 and 7168-2. The operation selection logic 7178 can be configured to control continuity of pass gates 7172-1 and 7172-2 based on a selected operation.

The sense amplifier 7170 can be operated to determine a data value (e.g., logic state) stored in a selected memory cell. The sense amplifier 7170 can comprise a cross coupled latch, which can be referred to herein as a primary latch. In the example illustrated in FIG. 7, the circuitry corresponding to sense amplifier 7170 comprises a latch 7175 including four transistors coupled to a pair of complementary digit lines D 6168-1 and (D)_7168-2. However, embodiments are not limited to this example. The latch 7175 can be a cross coupled latch (e.g., gates of a pair of transistors) such as n-channel transistors (e.g., NMOS transistors) 7182-1 and 7182-2 are cross coupled with the gates of another pair of transistors, such as p-channel transistors (e.g., PMOS transistors) 7184-1 and 7184-2). The cross coupled latch 7175 comprising transistors 7182-1, 7182-2, 7184-1, and 7184-2 can be referred to as the primary latch.

In operation, when a memory cell is being sensed (e.g., read), the voltage on one of the digit lines 7168-1 (D) or 7168-2 (D)_will be slightly greater than the voltage on the other one of digit lines 7168-1 (D) or 7168-2 (D)_. An ACT signal and an RNL* signal can be driven low to enable (e.g., fire) the sense amplifier 7170. The digit lines 7168-1 (D) or 7168-2 (D)_having the lower voltage will turn on one of the PMOS transistor 7184-1 or 7184-2 to a greater extent than the other of PMOS transistor 7184-1 or 7184-2, thereby driving high the digit line 7168-1 (D) or 7168-2 (D)_having the higher voltage to a greater extent than the other digit line 7168-1 (D) or 7168-2 (D)_is driven high.

Similarly, the digit line 7168-1 (D) or 7168-2 (D)_having the higher voltage will turn on one of the NMOS transistor 7182-1 or 7182-2 to a greater extent than the other of the NMOS transistor 7182-1 or 7182-2, thereby driving low the digit line 7168-1 (D) or 7168-2 (D)_having the lower voltage to a greater extent than the other digit line 76168-1 (D) or 7168-2 (D)_is driven low. As a result, after a short delay, the digit line 7168-1 (D) or 7168-2 (D)_having the slightly greater voltage is driven to the voltage of the supply voltage V_(CC) through a source transistor, and the other digit line 7168-1 (D) or 7168-2 (D)_is driven to the voltage of the reference voltage (e.g., ground) through a sink transistor. Therefore, the cross coupled NMOS transistors 7182-1 and 7182-2 and PMOS transistors 7184-1 and 7184-2 serve as a sense amplifier pair, which amplify the differential voltage on the digit lines 7168-1 (D) and 7168-2 (D)_and operate to latch a data value sensed from the selected memory cell on nodes 7177-1 and/or 7177-2.

Embodiments are not limited to the sense amplifier 7170 configuration illustrated in FIG. 7. As an example, the sense amplifier 7170 can be a current-mode sense amplifier and a single-ended sense amplifier (e.g., sense amplifier coupled to one digit line). Also, embodiments of the present disclosure are not limited to a folded digit line architecture such as that shown in FIG. 7.

The sense amplifier 7170 can, in conjunction with the compute component 7148, be operated to perform various operations using data from an array as input. In a number of embodiments, the result of an operation can be stored back to the array without transferring the data via a digit line address access (e.g., without firing a column decode signal such that data is transferred to circuitry external from the array and sensing circuitry via local I/O lines). As such, a number of embodiments of the present disclosure can enable performing operations and compute functions associated therewith using less power than various previous approaches. Additionally, since a number of embodiments eliminate the need to transfer data across local and global I/O lines in order to perform compute functions (e.g., between memory and discrete processor), a number of embodiments can enable an increased (e.g., faster) processing capability as compared to previous approaches.

The sense amplifier 7170 can further include equilibration circuitry 7174, which can be configured to equilibrate the digit lines 7168-1 (D) and 6768-2 (D)_. In this example, the equilibration circuitry 7174 comprises a transistor 7188 coupled between digit lines 7168-1 (D) and 7168-2 (D)_. The equilibration circuitry 7174 also comprises transistors 7180-1 and 7180-2 each having a first source/drain region coupled to an equilibration voltage (e.g., V_(DD)/2), where V_(DD) is a supply voltage associated with the array. A second source/drain region of transistor 7180-1 can be coupled digit line 7168-1 (D), and a second source/drain region of transistor 7180-2 can be coupled digit line 7168-2 (D)_. Gates of transistors 7188, 7180-1, and 7180-2 can be coupled together, and to an equilibration (EQ) control signal line 7186. As such, activating EQ enables the transistors 7188, 7180-1, and 7180-2, which effectively shorts digit lines 7168-1 (D) and 7168-2 (D)_together and to the equilibration voltage (e.g., V_(CC)/2).

Although FIG. 7 shows sense amplifier 76170 comprising the equilibration circuitry 7174, embodiments are not so limited, and the equilibration circuitry 7174 may be implemented discretely from the sense amplifier 7170, implemented in a different configuration than that shown in FIG. 7, or not implemented at all.

As described further below, in a number of embodiments, the sensing circuitry 7138 (e.g., sense amplifier 7170 and compute component 7148) can be operated to perform a selected operation and initially store the result in one of the sense amplifier 7170 or the compute component 7148 without transferring data from the sensing circuitry via a local or global I/O line (e.g., without performing a sense line address access via activation of a column decode signal, for instance).

However, further to embodiments described herein, sensing circuitry 7138 having sense amplifiers, and which in some embodiments may also include compute components as shown in FIGS. 9A and 9B, can also couple the memory cells from a multiplexed column of memory cells in an array to the compute components 9148-1, . . . , 9148-M and/or logic stripes 9152-1, . . . , 9152-N in a compute unit 9198 in the data path of the plurality of shared I/O lines 9144 local to the array as discussed in connection with FIGS. 9A and 9B. In this manner, the compute components 9148-1, . . . , 9148-M and/or logic stripes 9152-1, . . . , 9152-N may be indirectly coupled to the memory cells of a column through the plurality of shared I/O lines 9144 via select logic (discussed in connection with FIGS. 9A and 9B).

Performance of operations (e.g., Boolean logical operations involving data values) is fundamental and commonly used. Boolean logical operations are used in many higher level operations. Consequently, speed and/or power efficiencies that can be realized with improved operations, can translate into speed and/or power efficiencies of higher order functionalities.

As shown in FIG. 7, the compute component 7148 can also comprise a latch, which can be referred to herein as a secondary latch 7190. The secondary latch 7190 can be configured and operated in a manner similar to that described above with respect to the primary latch 7175, with the exception that the pair of cross coupled p-channel transistors (e.g., PMOS transistors) included in the secondary latch can have their respective sources coupled to a supply voltage 7176-2 (e.g., V_(DD)), and the pair of cross coupled n-channel transistors (e.g., NMOS transistors) of the secondary latch can have their respective sources selectively coupled to a reference voltage 7176-1 (e.g., ground), such that the secondary latch is continuously enabled. The configuration of the compute component 748 is not limited to that shown in FIG. 7, and various other embodiments are feasible.

As described herein, a memory device (e.g., 620 in FIG. 6A) can be configured to couple to a host (e.g., 602) via a data bus (e.g., 656) and a control bus (e.g., 654). A bank 6146 in the memory device 620 can include a plurality of bank sections (6150-1, . . . , 6150-N in FIG. 6) of memory cells. The bank 6146 can include sensing circuitry (e.g., 6138 in FIG. 6A and corresponding reference numbers in FIGS. 7 and 8) coupled to the plurality of arrays via a plurality of columns (FIG. 8) of the memory cells. The sensing circuitry can include a sense amplifier and a compute component (e.g., 7170 and 7148, respectively, in FIG. 7) coupled to each of the columns.

Each bank section 6150 can be associated with a plurality of logic stripes (e.g., 652-0, 5152-1, . . . , 56152-N−1 in FIG. 6B) in a compute unit in a data path of a plurality of shared I/O lines (6144 in FIG. 6B) local to array 725. A controller (e.g., 640 in FIGS. 6A-6B) coupled to the bank can be configured to direct, as described herein, movement of data values to a compute component 9148 (FIG. 9A) in a logic stripe 9152 (FIG. 9A) in a compute unit 8198/9198 (FIGS. 8 and 9A-9B) in a data path of a shared I/O line 8144/9144 (FIGS. 8 and 9A) local to the array.

The memory device can include a logic stripe (e.g., 6152 in FIG. 6B and 9152 in FIG. 9A) having a plurality of compute components (e.g., 9148-1, . . . , 9148-Z, respectively in FIG. 9A) that can correspond to a number of the plurality of columns (FIG. 6B) of the memory cells. As discussed further in connection with FIG. 7, the number of sense amplifiers 7170 and/or compute components 7148 in sensing circuitry 7138 can be selectably coupled (e.g., via column select circuitry 8194-1 and 8194-2 in FIG. 8) to a plurality of shared I/O lines 8144 (FIG. 8). The column select circuitry can be configured to selectably sense data in a particular column of memory cells of an array by being selectably coupled to a plurality of (e.g., four, eight, and sixteen, among other possibilities) sense amplifiers and/or compute components.

In some embodiments, a number of a plurality of logic stripes (e.g., 6152-1, . . . , 6152-N in FIG. 6B) in a bank can correspond to a number of bank sections 650-1, . . . , 5650-N in FIG. 6B (e.g., a quadrant having a plurality of subarrays) in the bank. A logic stripe can include a plurality of compute components 9148-1, . . . , 9148-Z (FIG. 9A) in a data path of a shared I/O local 9144 (FIG. 9A) to the array 725 that are like compute components 7148 shown in FIG. 67 As will be shown in FIG. 8 data values sensed from a row of the array can be moved in parallel by column select logic via a plurality of shared I/O lines 8144 (FIG. 78) to a plurality of compute components 9148 (FIG. 9A) in a compute unit 8198 (FIG. 8) a data path of the plurality of shared I/O lines 8144 (FIG. 8). In some embodiments, the amount of data can correspond to at least a thousand bit width of the plurality of shared I/O lines.

As described herein, the array of memory cells can include an implementation of DRAM memory cells where the controller is configured, in response to a command, to move (e.g., copy, transfer, and/or transport) data from the source location to the destination location via a shared I/O line. In various embodiments, the source location can be in a first bank and the destination location can be in a compute unit 8198 (FIG. 8 in a data path of the shared I/O lines 8144 (FIG. 8) local to the array 725.

As described in FIG. 8, the apparatus can be configured to move (e.g., copy, transfer, and/or transport) data from a source location, including a particular row (e.g., 819 in FIG. 7) and column address associated with a first number of sense amplifiers and compute components to a shared I/O line (e.g., 8144 in FIG. 8). In addition, the apparatus can be configured to move the data to a destination location, including a particular logic stripe 952 (FIG. 89) associated with a compute unit 9198 (FIG. 89) in a data path of the shared I/O line 8194 (FIG. 9A). As the reader will appreciate, each shared I/O line 9144 (FIG. 8) can actually include a complementary pair of shared I/O lines (e.g., shared I/O line and shared I/O line* in FIG. 8). In some embodiments described herein, 2048 shared I/O lines (e.g., complementary pairs of shared I/O lines) can be configured as a 2048 bit wide shared I/O line. In some embodiments described herein, 1024 shared I/O lines (e.g., complementary pairs of shared I/O lines) can be configured as a 1024 bit wide shared I/O line.

FIG. 8 is a schematic diagram illustrating circuitry for data movement in a memory device in accordance with a number of embodiments of the present disclosure. FIG. 8 shows eight sense amplifiers (e.g., sense amplifiers 0, 1, . . . , 7 shown at 8170-0, 8170-1, . . . , 8170-7, respectively) each coupled to a respective pair of complementary shared I/O lines 8144 (e.g., shared I/O line and shared I/O line*). FIG. 8 also shows eight compute components (e.g., compute components 0, 1, . . . , 7 shown at 8148-0, 8148-1, . . . , 8148-7) each coupled to a respective sense amplifier (e.g., as shown for sense amplifier 0 at 8170-0) via respective pass gates 8172-1 and 8172-2 and digit lines 8168-1 and 8168-2. For example, the pass gates can be connected as shown in FIG. 2 and can be controlled by an operation selection signal, Pass. For example, an output of the selection logic can be coupled to the gates of the pass gates 8172-1 and 8172-2 and digit lines 8168-1 and 8168-2. Corresponding pairs of the sense amplifiers and compute components can contribute to formation of the sensing circuitry indicated at 8138-0, 8138-1, . . . , 8138-7.

Data values present on the pair of complementary digit lines 8168-1 and 8168-2 can be loaded into the compute component 8148-0 as described in connection with FIG. 7. For example, when the pass gates 8172-1 and 8172-2 are enabled, data values on the pair of complementary digit lines 8168-1 and 8168-2 can be passed from the sense amplifiers to the compute component (e.g., 8170-0 to 8148-0). The data values on the pair of complementary digit lines 8168-1 and 8168-2 can be the data value stored in the sense amplifier 8170-0 when the sense amplifier is fired.

The sense amplifiers 8170-0, 8170-1, . . . , 8170-7 in FIG. 8 can each correspond to sense amplifier 7170 shown in FIG. 7. The compute components 8148-0, 8148-1, . . . , 8148-7 shown in FIG. 8 can each correspond to compute component 6148 shown in FIG. 7. A combination of one sense amplifier with one compute component can contribute to the sensing circuitry (e.g., 8138-0, 8138-1, . . . , 8138-7) of a portion of a DRAM memory subarray 8145 coupled to a shared I/O line 8144 shared by a number of logic stripes in a data path of the shared I/O lines 8144.

The configurations of embodiments illustrated in FIG. 8 are shown for purposes of clarity and are not limited to these configurations. For instance, the configuration illustrated in FIG. 8 for the sense amplifiers 8170-0, 8170-1, . . . , 8170-7 in combination with the compute components 8148-0, 8148-1, . . . , 8148-7 and the shared I/O line 8144 is not limited to half the combination of the sense amplifiers 8170-0, 8170-1, . . . , 8170-7 with the compute components 8148-0, 8148-1, . . . , 8148-7 of the sensing circuitry being formed above the columns 8192 of memory cells (not shown) and half being formed below the columns 8192 of memory cells. Nor are the number of such combinations of the sense amplifiers with the compute components forming the sensing circuitry configured to couple to a shared I/O line limited to eight. In addition, the configuration of the shared I/O line 8144 is not limited to being split into two for separately coupling each of the two sets of complementary digit lines 8168-1 and 8168-2, nor is the positioning of the shared I/O line 8144 limited to being in the middle of the combination of the sense amplifiers and the compute components forming the sensing circuitry (e.g., rather than being at either end of the combination of the sense amplifiers and the compute components).

The circuitry illustrated in FIG. 8 also shows column select circuitry 8194-1 and 8194-2 that is configured to implement data movement operations with respect to particular columns 8192 of a subarray 8145, the complementary digit lines 8168-1 and 8168-2 associated therewith, and the shared I/O line 8144 (e.g., as directed by the controller 640 shown in FIGS. 6A-6B). For example, column select circuitry 8194-1 has select lines 0, 2, 4, and 6 that are configured to couple with corresponding columns, such as column 0 (332-0), column 2, column 4, and column 6. Column select circuitry 8194-2 has select lines 1, 3, 5, and 7 that are configured to couple with corresponding columns, such as column 1, column 3, column 5, and column 7. The column select circuitry 8194 described in connection with FIG. 3 can, in various embodiments, represent at least a portion of the functionality embodied by and contained in multiplexers, e.g., an eight (8) way multiplexer, sixteen (16) way multiplexer, etc.

Controller 840 can be coupled to column select circuitry 8194 to control select lines (e.g., select line 0) to access data values stored in the sense amplifiers, compute components, and/or present on the pair of complementary digit lines (e.g., 8168-1 and 8168-2 when selection transistors 8196-1 and 8196-2 are activated via signals from select line 0). Activating the selection transistors 8196-1 and 8196-2 (e.g., as directed by the controller 540) enables coupling of sense amplifier 8170-0, compute component 8148-0, and/or complementary digit lines 8168-1 and 8168-2 of column 0 (8192-0) to move data values on digit line 0 and digit line 0* to shared I/O line 8144. For example, the moved data values may be data values from a particular row 819 stored (cached) in sense amplifier 8170-0 and/or compute component 8148-0. Data values from each of columns 0 through 7 can similarly be selected by the controller activating the appropriate selection transistors.

Moreover, enabling (e.g., activating) the selection transistors (e.g., selection transistors 8196-1 and 8196-2) can enable a particular sense amplifier and/or compute component (e.g., 8170-0 and/or 8148-0, respectively) to be coupled with a shared I/O line 8144 such that data values stored by an amplifier and/or compute component can be moved to (e.g., placed on and/or transferred to) the shared I/O line 8144. In some embodiments, one column at a time is selected (e.g., column 8192-0) to be coupled to a particular shared I/O line 8144 to move (e.g., copy, transfer, and/or transport) the stored data values. In the example configuration of FIG. 8, the shared I/O line 8144 is illustrated as a shared, differential/O line pair (e.g., shared/O line and shared/O line*). Hence, selection of column 0 (8192-0) could yield two data values (e.g., two bits with values of 0 and/or 1) from a row (e.g., row 819) and/or as stored in the sense amplifier and/or compute component associated with complementary digit lines 8168-1 and 8168-2. These data values could be input in parallel to each shared, differential/O pair (e.g., shared I/O and shared I/O*) of the shared differential/O line 8144.

FIG. 9A is a block diagram illustrating one of a plurality of sections 9150 of an array 925 coupled to a compute unit 9198, having a plurality of logic stripes 9152-1, . . . , 9152-N, by a plurality of shared I/O lines 9144 in a data path local to the array 925. In the example embodiment of FIG. 9A a bank section 9150 (e.g., bank quadrant) is shown having a plurality of subarrays 9145-1, . . . , 9145-32. In FIG. 9A, thirty-two (32) subarrays are illustrated in a bank quadrant 9150. However, embodiments are not limited to this example. This example shows a bank section having 16K columns which are multiplexed by sixteen (16) to the shared I/O lines 9144. Thus, 16K columns are multiplexed to 1K shared I/O lines 9144 such that every 16 columns can provide a data value that can be moved to the compute unit 9198 as a group of 1024 (1K) bits in parallel. Here, the shared I/lines 9144 provide a 1K bit wide data path to the compute unit 9198.

In the example of FIG. 9A, each logic stripe 9152-1, . . . , 9152-N has a plurality of compute components 9148-1, . . . , 9148-Z as the same have been described herein in connection with the sensing circuitry 7138 of FIG. 7. In some embodiments, each of the plurality of logic stripes 9152-1, . . . , 9152-N is configured to perform a compute function using the plurality of compute components 9148-1, . . . , 9148-Z. In some embodiments, each of the plurality of logic stripes 9152-1, . . . , 9152-Z can perform a different logical operation using the plurality of compute components 9148-1, . . . , 9148-Z. For example, in some embodiments at least one of the plurality of logic stripes 9152-1, . . . , 9152-Z can be configured to perform a long shift accelerator operation, e.g., eight (8) sixty-four (64) bit barrel shifter operation. This example could also provide a partial reorder in eight (8) bit chunks and could support a gather/scatter operation, in chunks of 256 bits with an 8 bit cross bar. In another example, in some embodiments at least one of the plurality of logic stripes 9152-1, . . . , 9152-Z can be configured to perform Kogge-Stone acceleration to generate a partial carry look ahead to accelerate a horizontal add. In another example, in some embodiments at least one of the plurality of logic stripes 9152-1, . . . , 9152-Z can be configured to perform “chunk” math acceleration. This example could provide vertical mode acceleration in small groups of bits (e.g., 4 or 8 bit chunks). In another example, in some embodiments the plurality of logic stripes 9152-1, . . . , 9152-Z can be configured to function as an explicit mask register to implement Boolean operations as would be used by a compiler. As used herein, a “chunk” is intended to reference a smaller bit length than an addressed row of data, e.g., a 256 bit chunk (within a 128 byte addressable row) may be addressed to match a bit width to a particular interface. This may be desirable to match a 256 bit interface of a 16K+ column memory array.

According to embodiments, the controller 540 (FIG. 5A) associated with the bank section can execute microcode instructions to direct movement of the 1K bit data values in parallel from each multiplexed column in connection with a particular accessed row among the plurality of subarrays 9145-1, . . . , 9145-32 to a particular compute component 9148-1, . . . , 9148-Z of a particular logic stripe 9152-1, . . . , 9152-N in the compute unit 9198.

According to some embodiments, a butterfly network 9202 can be used to connect the 1K bit data values to a respective one of the plurality of compute components 9148-1, . . . , 9148-Z in a respective one of the plurality of logic stripes 9152-1, . . . , 9152-N. By way of example, and not by way of limitation, 1K bits of data values can be moved in parallel to a logic strip associate with each of the 32 subarrays 9145-1, . . . , 9145-32 in each of 4 quadrants to a bank section 9150. In this example, 128 logic stripes 9152-1, . . . , 9152-N having 1K compute components 9148-1, . . . , 9148-Z each can be included in the compute unit 9198. Data values loaded to the plurality of compute components 9148-1, . . . , 9148-Z in the logic stripes 9152-1, . . . , 9152-N of the compute unit 9198 can be operated on according to microcode instructions from the controller 640 (FIG. 6A) to perform operations, e.g., AND, OR, NOR, XOR, add, subtract, multiply, divide, etc., on the data values as the same have been described herein in connection with the sensing circuitry 7138 of FIG. 7. As noted above, once the data values are loaded to the compute unit 9198, compute operations may be controlled in the compute unit much faster, e.g., at speeds of approximately 2 nanoseconds (ns), according to microcode instructions executed by the controller 640 (FIG. 6A) without having to move the data values back into the rows of the array 525 (FIG. 5A). For example, compute operations may be performed using the compute unit 9198 at a much faster speed as compared to an example time, e.g., approximately 60 nanoseconds (ns), that may be required to fire and access rows in the array 625 (FIG. 6A).

In the example embodiment of FIG. 7A, the plurality of compute components 9148-1, . . . , 9148-Z and/or logic stripes 9152-1, . . . , 9152-N in the compute unit 9198, in the data path of the plurality of shared I/O lines 9144, have a pitch equal to that of the data path of a shared I/O line. According to embodiments, the pitch of the data path is a function, e.g., multiple (2×, 4×, etc.), of a pitch of digit lines to the array 525 (FIG. 5A) of memory cells. For example, the plurality of compute components 9148-1, . . . , 9148-Z and/or logic stripes 9152-1, . . . , 9152-N have a pitch that is an integer multiple of the pitch of digit lines to the array of memory cells.

FIG. 9B is a block diagram example illustrating a plurality of arrays coupled to a plurality of compute components in a compute unit by a plurality of shared I/O lines in a data path local to the arrays where the compute component has a pitch equal to that of the data path of a shared I/O line and which is a multiple of a pitch of the digit lines to the array. The example of FIG. 9B illustrates a plurality of arrays, e.g., bank quadrants 9150-1, 9150-2, sections of arrays, etc., which may have memory cells accessed by digit lines 9168.

In the example of FIG. 9B, the bank quadrants 9150-1 and 9150-2 are shown having a pitch that is approximately sixteen thousand (16K) digit lines 9168 wide according to a given feature dimension (design rule) of a digit line fabrication process. Also shown are a plurality of shared I/O lines 9144-1, 9144-2, . . . , 9144-Z which can have a different pitch that is a function, e.g., multiple, of the given feature dimension (design rule) of the digit line fabrication process. In the example of FIG. 9B, the data path of the plurality of shared I/O lines 9144-1, 9144-Z have a pitch that is approximately sixteen (16) times greater than that of the digit lines 9168. Hence in this example, there are shown approximately one thousand (1K) shared I/O lines 9144-1, . . . , 9144-Z multiplexed to the 16K digit lines 9168 through 16:1 multiplexors, e.g., 9204-1, . . . , 9204-Z and 9206-1, . . . , 9206-Z, respectively. Embodiments, however, are not limited to the numerical example provided here and more or fewer digit lines 9168 may be multiplexed to a plurality of shared I/O lines 9144-1, . . . , 9144-Z. For example, the shared I/O lines 9144-1, . . . , 9144-Z can have a pitch that is a multiple other than 16 times (e.g., 16×) that of the pitch of the digit lines 9168 as set by a given feature dimension (design rule) of the digit line fabrication process.

As shown in the example of FIG. 9B, a compute component, e.g., among a plurality of compute components 9148-1, . . . , 9148-Z and 9149-1, . . . , 9149-Z, may be associated with each shared I/O line 9144-1, . . . , 9144-Z, respectively. The plurality of compute components 9148-1, . . . , 9148-Z and 9149-1, . . . , 9149-Z may be within a plurality of logic stripes, e.g., 9152-1, 9152-2, . . . , 9152-N shown in FIG. 9A, of a compute unit shown as 9198-1 and 9198-2, respectively. As shown in the example of FIG. 9B, a compute component, e.g., among a plurality of compute components 9148-1, . . . , 9148-Z and 9149-1, . . . , 9149-Z associated with each shared I/O line 9144-1, . . . , 9144-Z, may have a pitch that is equal to the data path of the shared I/O lines 9144-1, . . . , 9144-Z and hence sixteen times (e.g., 16×) that of the digit lines 9168 to the arrays, e.g., 9150-1 and 9150-2. According to various embodiments, since the compute components 9148-1, 9148-Z and 9149-1, . . . , 9149-Z in the data path of the shared I/O lines 9144-1, 9144-Z are not restricted in a one to one (e.g., 1× multiple) relationship with the pitch of the digit lines 8168, the compute components 9148-1, . . . , 9148-Z and 9149-1, . . . , 9149-Z are not limited to the “vertical” alignment of the arrays 8150-1 and 9150-2 and, in this example, can be sixteen times (16×) larger. As such, the compute components 9148-1, . . . , 9148-Z and 9149-1, . . . , 9149-Z in the data path of the shared I/O lines 9144-1, . . . , 9144-Z can be used to perform more robust set of logical operations on data values stored therein (e.g., by having a larger footprint and space) such as the above mentioned long shift acceleration, while still being proximate to the arrays 9150-1 and 9150-1 and not off in a peripheral area of the array or memory die.

Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results can be substituted for the specific embodiments shown. This disclosure is intended to cover adaptations or variations of various embodiments of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of the various embodiments of the present disclosure includes other applications in which the above structures and methods are used. Therefore, the scope of various embodiments of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed embodiments of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

What is claimed is:
 1. An apparatus, comprising: a number of memory arrays; and a controller, wherein the controller is configured to cause the apparatus to: perform an artificial intelligence (AI) operation on data stored in the number of memory arrays; and perform a debug operation on the artificial intelligence (AI) operation.
 2. The apparatus of claim 1, wherein the AI operation stops in response to performing the debug operation.
 3. The apparatus of claim 1, wherein the apparatus includes a number of registers.
 4. The apparatus of claim 3, wherein the number of registers include a first register to stop the A operation.
 5. The apparatus of claim 1, wherein the debug operation includes storing errors from the AI operation.
 6. An apparatus, comprising: a number of memory arrays; and a controller, wherein the controller is configured to: receive, from a host, a debug command to perform a debug operation on an artificial intelligence (AI) operation performed on the apparatus; and execute the debug command by causing performance of the debug operation on the artificial intelligence (AI) operation.
 7. The apparatus of claim 6, wherein the AI operation uses input data and neural network data.
 8. The apparatus of claim 6, wherein the AI operation uses partial results of AI operations and bias value data.
 9. The apparatus of claim 6, wherein the AI operation uses partial results of AI operations and activation function data.
 10. The apparatus of claim 6, wherein the debug operation includes storing data of the AI operation in a temporary memory block of the number of memory arrays.
 11. The apparatus of claim 10, wherein the temporary memory block is validated.
 12. The apparatus of claim 6, wherein the debug operation includes storing a result of the debug operation in a temporary memory block of the number of memory arrays.
 13. The apparatus of claim 6, wherein a result of the debug operation is sent to a host.
 14. An apparatus, comprising: a number of memory arrays; and a controller, wherein the controller is configured to cause the apparatus to: enable performance of a debug operation on an artificial intelligence (AI) operation by writing an indicator in a register to a particular state in response to receiving a command from a host.
 15. The apparatus of claim 14, wherein a first bit of the register is programmed to a first state to start the debug operation.
 16. The apparatus of claim 14, wherein a second bit of the register is programmed to a first state to indicate the A operation can step forward.
 17. The apparatus of claim 14, wherein a third bit of the register is programmed to a first state to indicate a temporary block is valid.
 18. The apparatus of claim 14, wherein a fourth bit of the register is programmed to a first state to store data from the A operation.
 19. The apparatus of claim 14, wherein a fifth bit of the register is programmed to a first state to send a result of the debug operation to a host.
 20. The apparatus of claim 14, wherein a sixth bit of the register is programmed to a first state to store a result of the debug operation.
 21. A method, comprising: performing an artificial intelligence (AI) operation on data stored in a number of memory arrays; and performing a debug operation on the artificial intelligence (AI) operation.
 22. The method of claim 21, further comprising updating a neural network based on a result of the debug operation.
 23. The method of claim 21, further updating a bias value based on a result of the debug operation.
 24. The method of claim 21, further comprising updating an activation function based on a result of the debug operation.
 25. The method of claim 21, further comprising updating input data based on a result of the debug operation. 